Data transmission method and apparatus, and data reception method and apparatus

ABSTRACT

Provided are a data transmission method and apparatus, and a data reception method and apparatus. The data transmission method comprises steps of: generating at least one total downlink assignment index for a plurality of component carrier groups; and carrying the at least one total downlink assignment index in downlink control information to transmit the same to a receiving end.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of U.S. patent applicationSer. No. 16/753,320, filed on Apr. 20, 2020, which is based upon andclaims benefit of Chinese patent application No. 201711230884.X filed onNov. 29, 2017 in the China National Intellectual PropertyAdministration, the contents of which are incorporated herein byreference in their entirety.

FIELD OF THE INVENTION

The present disclosure relates to the field of communication, and inparticular, to a data transmission method and apparatus, and a datareception method and apparatus.

BACKGROUND

In the related art, in a new-generation wireless communication (New RAT,NR) system, some new technical features are introduced, which putsforwards new demands on determination of a Hybrid Automatic RepeatRequest (HARQ) feedback codebook.

On one hand, the NR system supports Carrier Aggregation (CA) betweenComponent Carriers (CCs) with different Subcarrier Spacings (SCSs). Inthis regard, unlike the Long Term Evolution (LTE) system, slots of CCswith different subcarrier spacings have different lengths. How tosupport dynamic codebook determination during aggregation between CCswith different subcarrier spacings is a problem to be solved.

On the other hand, uplink feedback timing of a terminal is dynamicallyconfigured, that is, a network side configures an uplink feedback timingset semi-statically through a Radio Resource Control (RRC) signaling,and further dynamically indicates in a Downlink Control Indication (DCI)which value in the set is the timing adopted by the current slot. Thismakes the feedback more flexible, but the size of the feedback codebookbecomes more dynamic.

In addition, the NR system supports a feedback based on a Code BlockGroup (CBG), that is, an original Transmission Block (TB) is dividedinto a plurality of CBGs, and the terminal receives downlink data inunits of CBGs and performs feedback on the received CBGs one by one. Themain advantage of doing so is in that the retransmitted data size can bereduced, and under the original feedback mechanism based on the TB, theterminal can only feed back Acknowledgement (ACK)/No Acknowledgement(NACK) according to the situation of receiving whole TB, and when thebase station receives the feedback of the terminal, the TB correspondingto the No Acknowledgement (NACK) can be retransmitted as a whole; undera feedback mechanism based on the CBG, the terminal respectively feedsback a plurality of CBGs in the TB, and the base station onlyretransmits the CBGs which feed back NACK. Adding ACK or NACK feedbackcodebook determination in a CBG feedback mode is also a problem to beconcerned.

In view of the problem of lack of a determination mechanism scheme of afeedback codebook in the related art, no effective solution exists atpresent.

SUMMARY

The embodiments of the present disclosure provide a data transmissionmethod and apparatus and a data reception method and apparatus, to atleast solve the problem of lack of a determination mechanism scheme of afeedback codebook in the related art.

According to an embodiment of the present disclosure, there is provideda data transmission method, including: generating at least one totaldownlink assignment index for a plurality of component carrier groups;and carrying the at least one total downlink assignment index indownlink control information to transmit to a receiving end.

According to another embodiment of the present disclosure, there isfurther provided a data reception method, including: receiving aplurality of total downlink assignment indexes, wherein the plurality oftotal downlink assignment indexes correspond to a plurality of componentcarrier groups; and determining a size of a feedback codebook of thecorresponding component carrier groups according to the plurality oftotal downlink assignment indexes.

According to another embodiment of the present disclosure, there isfurther provided a data transmission apparatus, including: a generationmodule configured to generate at least one total downlink assignmentindex for a plurality of component carrier groups; and a transmissionmodule configured to carry the at least one total downlink assignmentindex in downlink control information and transmit to a receiving end.

According to another embodiment of the present disclosure, there isfurther provided a data reception apparatus, including: a receptionmodule configured to receive a plurality of total downlink assignmentindexes, wherein the plurality of total downlink assignment indexescorrespond to a plurality of component carrier groups; and adetermination module configured to determine a size of a feedbackcodebook of the corresponding component carrier groups according to theplurality of total downlink assignment indexes.

According to another embodiment of the present disclosure, there isfurther provided a storage medium including a stored program, whereinthe stored program, when executed, performs the method according to anyone of the subsequent embodiments.

According to another embodiment of the present disclosure, there isfurther provided a processor configured to execute a program, whereinthe program, when executed by the processor, performs the methodaccording to any one of the subsequent alternative embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

The drawings described herein are intended to provide a furtherunderstanding of the disclosure and form a part of the disclosure. Theillustrative embodiments of the present disclosure and the descriptionthereof are used to explain the disclosure and do not constitute anundue limitation. In the drawings:

FIG. 1 is a block diagram showing a hardware structure of a base stationof a data transmission method of an embodiment of the disclosure;

FIG. 2 is a process diagram of a data transmission method according toan embodiment of the disclosure;

FIG. 3 is a schematic diagram according to an Applicable embodiment 1;

FIG. 4 is a schematic diagram according to a Sub-embodiment 2.3 of anApplicable embodiment 2;

FIG. 5 is a schematic diagram according to a Sub-embodiment 2.4 of theApplicable embodiment 2;

FIG. 6 is a schematic diagram according to a Sub-embodiment 2.5 of theApplicable embodiment 2;

FIG. 7 is a schematic diagram according to an Applicable embodiment 3;

FIG. 8 is a schematic diagram according to an Applicable embodiment 4;

FIG. 9 is a schematic diagram according to an Applicable embodiment 5;

FIG. 10 is a schematic diagram according to an Applicable embodiment 6;

FIG. 11 is a schematic diagram according to an Applicable embodiment 7;

FIG. 12 is another schematic diagram according to the Applicableembodiment 7;

FIG. 13 is a schematic diagram according to an Applicable embodiment 8;and

FIG. 14 is another schematic diagram according to the Applicableembodiment 8.

DETAILED DESCRIPTION OF THE EMBODIMENTS

In an embodiment of the present disclosure, there is provided a mobilecommunication network (including but not limited to a 5G mobilecommunication network), and a network architecture of the network mayinclude a network side device (e.g., a base station) and a terminal. Inthe embodiment, there is provided a data transmission method that iscapable of operating on the above network architecture. It should benoted that, the operation environment of the data transmission methodaccording to the embodiments is not limited to the network architecture.

Embodiment 1

A process embodiment according to Embodiment 1 of the present disclosuremay be executed in a base station, a mobile terminal, or a similarcomputing device. Taking an operation on a base station as an example,FIG. 1 is a block diagram showing a hardware structure of a base stationof a data transmission method of an embodiment of the presentdisclosure. As shown in FIG. 1 , a base station 10 may include at leastone processor 102 (only one is shown in the figure, and the processor102 may include but is not limited to a processing device such as amicroprocessor (Microcontroller unit, MCU) or a programmable logicdevice (Field Programmable Gate Array, FPGA)), a memory 104 configuredto store data, and a transmission apparatus 106 configured to perform acommunication function. It will be appreciated by those skilled in theart that the structure as shown in FIG. 1 is only for illustration andis not intended to limit the structure of the electronic apparatus. Forexample, the base station 10 may further include more or less componentsthan those as shown in FIG. 1 , or have different configurations thanthose as shown in FIG. 1 .

The memory 104 may be configured to store software programs and modulesof application software, such as program instructions/modulescorresponding to the data transmission method in the embodiment of thedisclosure, and the processor 102 executes various functionalapplications and data processing by executing the software programs andmodules stored in the memory 104, so as to implement the methoddescribed above. The memory 104 may include a high-speed random accessmemory, and may also include a non-volatile memory, such as at least oneof: a magnetic storage apparatus, a flash memory, or other non-volatilesolid-state memory. In some examples, the memory 104 may includememories remotely located from the processor 102, and these memories maybe connected to the base station 10 through networks. Examples of suchnetworks include, but are not limited to, the Internet, intranets, localarea networks, mobile communication networks, and combinations thereof.

A transmission apparatus 106 is configured to receive or transmit datavia a network. Examples of such network applications may includewireless networks provided by a communication provider of the basestation 10. In one example, the transmission apparatus 106 includes anetwork adapter (Network Interface Controller, MC) that can be connectedto other network devices through a base station so as to communicatewith the Internet. In one example, the transmission apparatus 106 may bea Radio Frequency (RF) module configured to communicate with theInternet in a wireless manner.

In a Long Term Evolution (LTE) system in the related art, a terminalperforms feedback based on a Transmission Block (TB), and in a TimeDivision Duplexing (TDD) mode, a plurality of downlink transmissionslots of the terminal may correspond to one uplink transmission slot,and at this time, the feedback for a plurality of downlink schedules maybe aggregated on one uplink transmission resource (which may be aPhysical Uplink Control Channel (PUCCH) or a Physical Uplink SharedChannel (PUSCH)). When Hybrid Automatic Repeat Request (HARQ)multiplexing is applied, the size of the feedback codebook depends onthe number of slots and the number of codewords within the feedbackwindow, and in a carrier aggregation scenario, the size of the feedbackcodebook is also related to the number of component carriers. The basestation and the terminal need to have uniform knowledge on the size andsequence of the codebook, so as to avoid causing wrong retransmission.

One feedback codebook determination mode is a semi-static codebook, thatis, for the downlink transmission resource within the feedback timewindow, no matter whether the base station schedules the downlink dataof the terminal in a slot of a component carrier, the terminal will feedback for each slot of each carrier component. Obviously, since part ofthe downlink resource does not schedule the terminal, some feedbacks areuseless overhead.

Another feedback codebook determination mode is a dynamic codebook,where a concept of Downlink Assignment index (DAI) is introduced, forexample, a Downlink Control Information (DCI) corresponding to aDownlink Assignment (DL Assignment) includes a counter DownlinkAssignment index (counter DAI) indication field for indicating to theterminal which slot schedules the downlink data of the terminalactually, and a Total Downlink Assignment index (Total DAI) indicationfield is included in the DCI which includes uplink grant (UL grant), forindicating a total number of Downlink assignments required to be fedback. The terminal determines the size of the dynamic codebook accordingto the Total DAI, so that the terminal can save part of useless feedbackoverhead in the semi-static codebook. When the terminal does not haveuplink grant at the moment, Total DAI does not exist, and the feedbackcodebook is returned to be a semi-static codebook. The introduction ofDAI increases the overhead of downlink control information. In anembodiment, in an LTE Carrier Aggregation (CA) scenario, when the numberof component carriers is small (for example, not more than 5), the samemanner as the above dynamic codebook mechanism under single carrier isadopted, and at this time, the counter DAI pair is aggregated to becounted in the entirety of a plurality of CCs, and the Total DAI is atotal number of downlink assignments of the plurality of CCs.

In this embodiment, there is provided a data transmission methodoperating on the network architecture, which can be used on a basestation side. FIG. 2 is a process diagram of a data transmission methodaccording to an embodiment of the disclosure. As shown in FIG. 2 , theprocess includes the following steps S202 and S204.

In step S202, at least one total downlink assignment index is generatedfor the plurality of component carrier groups.

In step S204, the at least one total downlink assignment index iscarried in downlink control information to be transmitted to a receivingend.

Through the steps, at least one total downlink assignment index isgenerated for the plurality of component carrier groups; and the atleast one total downlink assignment index is carried in the downlinkcontrol information to be transmitted to the receiving end. In the datatransmission method of the present disclosure, the downlink controlinformation includes a plurality of total downlink assignment indexesused for downlink assignment instructions of a plurality of componentcarrier groups, which improves a situation where a feedback codebookdetermination mechanism scheme is lacking in related art. After thefeedback codebook determination mechanism of the above scheme is adaptedto the new requirements introduced in the new system NR, the dynamiccodebook needs to be processed in groups, and a plurality of totaldownlink assignment indexes may occur.

In an embodiment, the component carriers are divided into the pluralityof component carrier groups according to at least one piece of: codeblock group configuration information of component carriers; a slotlength or a subcarrier spacing of the component carriers; and codewordconfiguration information of the component carriers.

In an embodiment, the code block group configuration informationincludes at least one of: the number of code block groups included in aslot; and the number of code block groups included in a transmissionblock.

In an embodiment, the codeword configuration information includes atleast one of: the number of codewords included in a slot; and the numberof codewords included in a transmission block.

In an embodiment, the step of generating at least one total downlinkassignment index for the plurality of component carrier groups includesat least one of: each of the generated total downlink assignment indexescorresponding to a component carrier group; and the number of the atleast one of the generated total downlink assignment indexes being lessthan or equal to the number of the plurality of component carriergroups.

In an embodiment, the total downlink assignment index is used toindicate the number of downlink assignments required to be fed back in aspecified uplink slot before an uplink grant in the component carriergroup corresponding to the total downlink assignment index; wherein thenumber of the downlink assignments includes at least one of: the numberof slots carrying the downlink assignments; and the total number of thecode block groups in all the slots carrying the downlink assignments. Itis necessary to supplement that the meaning of the above alternativeembodiments may be as follows: the number of downlink assignmentscomprises the number of slots which carry the downlink assignments; or,the number of downlink assignments is the total number of code blockgroups in the slots which are all slots carrying downlink assignments.

In an embodiment, the specified uplink slot comprises: the uplink slotindicated by the uplink grant.

In an embodiment, the uplink grant and the total downlink assignmentindex are transmitted in the same downlink control information.

In an embodiment, the step of carrying the at least one total downlinkassignment index in the downlink control information to be transmittedto the receiving end comprises at least one of: setting, in the downlinkcontrol information, a first information field for carrying the at leastone total downlink assignment index, according to the maximum number ofthe total downlink assignment indexes, wherein a bit number occupied bythe first information field is equal to a bit number required when thetotal downlink assignment indexes having the maximum number aretransmitted; setting, in the downlink control information, a secondinformation field for carrying the at least one total downlinkassignment index, according to the current number of the total downlinkassignment indexes, wherein a bit number occupied by the secondinformation field is equal to a bit number required when the totaldownlink assignment indexes having the current number are transmitted;setting, in the downlink control information, a third information fieldfor carrying one total downlink assignment index; wherein, when thenumber of the total downlink assignment indexes is more than one,information fields except the third information field in the downlinkcontrol information are multiplexed to carrying residual total downlinkassignment indexes, wherein a bit number occupied by the thirdinformation field is equal to a bit number required when the one totaldownlink assignment index is transmitted; multiplexing, in the downlinkcontrol information, a specified information field in the downlinkcontrol information to carry the at least one total downlink assignmentindex; and multiplexing, in the downlink control information, thespecified information field in the downlink control information to carrythe total downlink assignment index, wherein, under the condition thatthe bit number which the specified information field is able to carry issmaller than the bit number required when a plurality of total downlinkassignment indexes are transmitted, a fourth information field to carrythe residual total downlink assignment indexes is set, wherein a bitnumber occupied by the fourth information field is equal to a bit numberrequired when the residual total downlink assignment indexes aretransmitted.

In an embodiment, the specified information field in the downlinkcontrol information comprises at least one of: an indication informationfield of uplink grant timing; and an indication information field ofcode block group transmission.

In an embodiment, the third information field is used to carry a totaldownlink assignment index corresponding to a component carrier groupwhere the third information field is located.

According to another embodiment of the disclosure, there is furtherprovided a data reception method, applicable to a terminal, includingthe following Step 1 and Step 2.

At Step 1, receiving, in downlink control information, at least onetotal downlink assignment index, wherein the at least one total downlinkassignment index corresponds to a plurality of component carrier groups;

At Step 2, determining the size of the feedback codebook of thecorresponding component carrier group according to the at least onetotal downlink assignment index.

In an embodiment, after receiving at least one total downlink assignmentindex in the downlink control information, according to the totaldownlink assignment index, the following information is determined: thenumber of downlink assignments required to be fed back in a specifieduplink slot before an uplink grant in the component carrier groupcorresponding to the total downlink assignment index; wherein the numberof the downlink assignments includes at least one of: the number ofslots carrying the downlink assignments; and the total number of thecode block groups carrying all the slots of the downlink assignments.

In an embodiment, the specified uplink slot includes the uplink slotindicated by the uplink grant.

In an embodiment, the uplink grant information and the total downlinkassignment index are received in the same downlink control information.

The following description will be made in detail with reference toapplicable embodiments.

Applicable Embodiment 1

This embodiment describes a situation where aggregated CCs are groupedaccording to CBG configuration, a plurality of component Carrier Groups(CGs) all use a dynamic codebook, and total downlink assignment indexes(Total DAIs) corresponding to all CGs are transmitted in DCI of the sameCC.

FIG. 3 is a schematic diagram according to Application Example 1. Asshown in FIG. 3 , a total of 5 CCs are included to operate in a carrieraggregation CA manner, namely CC #0 to CC #4, for example, theconfiguration shown in Table 1. Table 1 is a configuration table of CC#0 to CC #4 according to the Applicable embodiment 1:

TABLE 1 CC CBG configuration Subcarrier spacing (SCS) CG #0 4 15 kHz CG1#1 4 60 kHz CG1 #2 4 30 kHz CG1 #3 8 15 kHz CG2 #4 8 30 kHz CG2

The aggregated CCs are divided into two CGs according to CBGconfiguration, CG1 including CC #0, CC #1, CC #2; CG2 including CC #3,CC #4.

The counter DAI is used to count in two CGs respectively, i.e. a counterDAI field is included in each DCI including DL assignment, forindicating which the scheduled slot in the CG required to be fed back inthe same slot is the current slot. The counting sequence adopts aprinciple of frequency domain priority, that is, slots including DLassignment on all CCs are accumulated at the monitoring occasion of theprevious Physical Downlink Control Channel (PDCCH) first, for example,for CG1, the terminal is scheduled by DCIs of CC #0 and CC #1 at thefirst PDCCH monitoring occasion, that is, the DCIs include DLassignment, and counter DAI fields of each DCI are respectivelyindicated as 0 and 1, indicating that the current slot is the first andsecond scheduled slots in the CG, respectively (note: DAI is countedfrom ‘0’ and is cyclically counted at a period of 4, i.e., 01230123 . .. ), such a cycle count is to ensure that only 2 bits can be used toindicate any DAI value in the DCI). Then, a second PDCCH monitoringoccasion is accumulatively counted. Since the subcarrier spacings ofdifferent CCs in the CG are different, the TTI lengths are alsodifferent, and the second PDCCH monitoring occasion is only valid for CC#1, and at this time, the terminal is scheduled by CC #1, and thecounter DAI field of the DCI is indicated as 2. By analogy, the count ofDL assignment of all slots before the UL grant is received within thefeedback time window is completed; and the feedback information of theDL assignment is all transmitted to the base station in the slotindicated by the UL grant.

For CG2, the same mechanism as described above is also used for thecumulative count of counter DAI.

In the 5 CCs, only CC #4 includes an uplink slot, wherein the uplinkslot refers to a slot including at least one of a physical uplinkcontrol channel PUCCH and a physical uplink shared channel PUSCH;therefore, the uplink feedback for 5 CCs is transmitted on CC #4,correspondingly the UL grant is also transmitted on CC #4, and DCIincluding the UL grant includes not only scheduling information ofuplink data, but also Total DAI, for indicating the number of slotsincluding DL assignment in the plurality of CGs, and in this embodiment,two CCs are included, so that DCI including UL grant includes two TotalDAI fields for indicating the number of slots including DL assignment inCG1 and CG2, and the values thereof are 2 and 3, respectively.

The terminal can determine the size of the feedback codebook accordingto the reception of the Total DAI in combination with the reception of aplurality of DL assignments. Namely, there are 7 slots including the DLassignments in CG 1; and there are 4 slots including the DL assignmentsin CG 2. The codebook size is also related to the CBG configuration andthe codeword configuration (assuming codeword configuration is 2, i.e.only two codewords are transmitted by each slot), CBG configuration is 4in CG1, i.e. the feedback bits not required by each slot including DLassignments in CG1 are N_(CBG)*N_(codeword)=4*2=8, and then the totalbits that CG1 needs to feed back areN_(CBG)*N_(codeword)*N_(slot)=8*7=56 bits. Similarly, the total bitsthat CG2 needs to feed back are N_(CBG)*N_(codeword)*N_(slot)=8*2*4=64bits. The two parts of feedback bits are cascaded together, and thetotal bit number required by the terminal to be fed back in the uplinkfeedback resource is 120 bits.

In addition, when there is a UL grant (i.e., the terminal schedulesuplink data and assigns PUSCH resources), the uplink feedback of theterminal is multiplexed with the uplink data in the PUSCH andtransmitted, where the multiplexing mode may be that the feedbackinformation performs puncturing transmission on the uplink data, or theuplink data performs rate matching transmission around the feedbackinformation.

It should be appreciated that, the Total DAI and the UL grant aretransmitted in the same DCI, the Total DAI indicates the number of allslots including DL assignments before the UL grant. If there are furtherDL assignments of the terminal after the UL grant and feedback is neededin the same feedback slot, Total DAI cannot predict the numberindicating this part of DL assignments, a new mechanism will be neededto indicate this part of DL assignments to, and the feedback bit numberwill be accumulatively counted to the above total bit number forfeedback together; or, the terminal will not be allowed to be furtherscheduled after the UL grant. As shown in the figure, the subcarrierspacing of the CC in which the UL grant is located is 30 kHz, and the ULgrant is transmitted in the DCI of the last slot of 30 kHz, where thelast slot of CC #1 (subcarrier spacing 60 kHz) is not allowed toschedule the terminal.

Applicable Embodiment 2

This applicable embodiment describes how to transmit a plurality ofTotal DAI information fields in one DCI.

This applicable embodiment includes the following severalsub-embodiments:

Sub-embodiment 2.1: an information field is defined according to amaximum value of the bits required by a plurality of Total DAIs;

The plurality of component carriers are divided into the plurality ofcomponent carrier groups according to at least one of: code block groupconfiguration information of component carriers; a slot length or asubcarrier spacing of the component carriers; and codeword configurationinformation of component carriers.

It can be seen that the maximum number of component carrier groups isfixed on the any one grouping basis. For example, when groupingaccording to CBG configuration, the protocol specifies that the CBGconfiguration includes 4 values: 2, 4, 6, and 8. The maximum number ofcomponent carrier groups is 4. Accordingly, when each CG corresponds toa Total DAI, 4 Total DAI fields are required at the maximum. In the DCI,according to the maximum value of the number of the total downlinkassignment indexes, a first information field is defined to carry theplurality of total downlink assignment indexes; at this time, 4 TotalDAI fields are fixedly configured in DCI no matter how many CGs areactually presented at current. The bit number of the first informationfield is equal to the bit number required when the total downlinkassignment indexes having the maximum number are transmitted.

Each Total DAI field requires 2 bits, then 4 Total DAI fields arefixedly defined, and Total DAI information fields (the first informationfield) are 8 bits. When the actual CG number is less than 4, only theTotal DAI corresponding to the CG is indicated by using the part ofTotal DAI fields. Unused Total DAI fields are invalid. Since there isconsistent knowledge on how the CCs are grouped and how many groups areformed between the terminal and the base station, and further sincewhich Total DAI field corresponds to which CG is determined according topredefined rules (e.g., the Total DAI field including the 2nd bitcorresponds to the minimum CBG configuration, the Total DAI fieldsincluding the 3rd and 4th bits from the bottom correspond to the CGwhere CBG configuration is 4, and so on), the terminal can determinewhich Total DAI fields are valid and which Total DAI fields are invalid.No ambiguity arises.

For another example, when CC grouping is performed according to the slotlength of the component carrier, the types of the slot lengths supportedby the specific frequency band range are fixed. For example, thefrequency bands below 6 GHz include 3 slot lengths: 0.25 ms, 0.5 ms, 1ms. Thus, the number of CGs is at most 3, the first information field isdefined as 6 bits, corresponding to three Total DAI fields.

For another example, when the CC grouping is performed based on the CodeBlock Group (CBG) configuration and the subcarrier spacing of thecomponent carriers, the CBG configuration has 4 values, and thesubcarrier spacing has 2 values in a specific frequency band (e.g., afrequency band above 6 GHz), the number of CGs is at most 8, and thefirst information field is defined as 16 bits, corresponding to 8 TotalDAI fields.

Sub-embodiment 2.2: an information field is defined according to the bitnumber required by the Total DAI having the current number;

In the aggregated CCs, the CBG configuration of the plurality of CCs andthe subcarrier spacing or the slot length of the plurality of CCs areall determined semi-statically, for example, configured to the terminalthrough RRC signaling; therefore, the CBG configuration, the subcarrierspacing or the slot length configuration of the plurality of CCs withina specified feedback window is determined. The actual CG number is alsodetermined. Further, the number of the Total DAI fields is determined,and the number of bits required is also determined.

For example, only two CBG configurations, 4 and 8, are included in thecurrently aggregated CCs. That is, when the CCs are grouped according tothe CBG configuration, there are two CGs. Therefore, in the DCI,according to the number of the current total downlink assignmentindexes, a second information field is defined to carry the plurality oftotal downlink assignment indexes; the second information fieldcorresponds to the number of bits required when the total downlinkassignment indexes having the current number are transmitted. The secondinformation field includes two Total DAI fields. If each Total DAI fieldrequires 2 bits, the second information field occupies a Total of 4bits.

Sub-embodiment 2.3: a part of the Total DAI fields are transmitted onthe newly defined information fields, and a part of the Total DAI fieldsmultiplex other information fields in the DCI;

In an embodiment, other information fields within the DCI include atleast one of:

an uplink grant timing indication information field (configured toindicate the time domain position of the scheduled uplink data, i.e.,the time interval between the uplink grant UL grant and thecorresponding PUSCH, and when the timing information is a default value,the indication field is invalid and may be configured to indicate otherinformation);

A Code Block Group Transmission Indication (CBGTI) information field(configured to indicate which code block groups are retransmittedcurrently, and when the transmission data is new transmission data, theindication field is invalid and can be configured to indicate otherinformation).

FIG. 4 is a schematic diagram according to Sub-embodiment 2.3 ofApplicable embodiment 2. As shown in FIG. 4 , a DCI format including aUL grant is illustrated, wherein the DCI format includes, but is notlimited to, the following information fields: an uplink grantinformation field, a CBG TI information field, an uplink schedulingtiming information field K2, and a Total DAI field (or total DAI field).

In some cases, the CBG TI information field, and the uplink schedulingtiming information field are not used. For example, when the uplinkgrant is a new transmission data for scheduling the terminal, the basestation does not need to indicate the CBG TI information field to theterminal, and at this time, the CBG TI information field may beredefined, i.e., used to transmit part of Total DAI fields. Similarly,when the uplink grant uses a fixedly or implicitly indicated timingrelationship, the base station does not need to indicate the uplinkgrant timing indication information K2 to the terminal by using theuplink scheduling timing information field, and at this time, the uplinkgrant timing indication information field may also be redefined, thatis, used to transmit part of Total DAI fields.

In this embodiment, in the DCI, a third information field is defined tocarry the one total downlink assignment index, and when the number ofthe total downlink assignment indexes is greater than one, otherinformation fields in the multiplexing downlink control informationcarry other total downlink assignment indexes; wherein the thirdinformation field corresponds to the number of bits required when theone total downlink assignment index is transmitted.

In an embodiment, the third information field transmits the Total DAI ofthe CG where the third information field is located. When the CBG TIinformation field and the uplink grant timing indication informationfield can be used, they may be used to transmit the Total DAI of otherCGs. If the current uplink grant timing indication information field andthe CBG TI field are both valid, the DCI will not include the Total DAIinformation of other CGs.

Sub-embodiment 2.4: other information fields in the DCI are multiplexedto transmit the plurality of Total DAI fields.

In an embodiment, other information fields in the DCI include at leastone of: an uplink grant timing indication information field (configuredto indicate the time domain position of the scheduled uplink data, i.e.,the time interval between the uplink grant UL grant and thecorresponding PUSCH, and when the timing information is a default value,the indication field is invalid and may be configured to indicate otherinformation);

A Code Block Group Transmission Indication (CBGTI) information field(configured to indicate which code block groups are retransmittedcurrently, and when the transmission data is new transmission data, theindication field is invalid and may be configured to indicate otherinformation). FIG. 5 is a schematic diagram according to Sub-embodiment2.4 of Applicable embodiment 2. As shown in FIG. 5 , a DCI formatincluding a UL grant is illustrated, wherein the DCI format includes,but is not limited to, the following information fields: an uplink grantinformation field, a CBG TI information field, and an uplink granttiming indication information field.

As in the foregoing description, in some cases, the CBG TI informationfield and the uplink grant timing indication information field are notused. At this time, these information fields may be redefined, i.e.,used to transmit part of the Total DAI field.

Sub-embodiment 2.5: a designated information field is multiplexed in theDCI to transmit the plurality of Total DAI fields, and a fourthinformation field is defined for carrying the residual total downlinkassignment indexes when the bit number which the designated informationfield is able to carry is less than the bit number required by theplurality of total downlink assignment indexes.

As described in sub embodiment 2.4, when the CBG TI information fieldand the uplink scheduling timing information field are not used, theymay be redefined and used to transmit the Total DAI field. When the bitnumber which other information fields are able to carry is smaller thanthe bit number required by the plurality of total downlink assignmentindexes, a fourth information field is defined to carry the residualtotal downlink assignment indexes, wherein the fourth information fieldcorresponds to the bit number required when the residual total downlinkassignment indexes are transmitted.

For example, 4 bits of other information fields may be used for TotalDAI, i.e., 2 Total DAI fields may be transmitted. 4 Total DAI fields arecurrently required to be transmitted, and thus additional fields may bedefined for two more Total DAI fields, and the fourth information fieldmay be 4 bits.

In an embodiment, FIG. 6 is a schematic diagram according toSub-embodiment 2.5 of Applicable embodiment 2, and as shown in FIG. 6 ,one Total DAI field is included in the uplink grant timing indicationinformation field and the CBG TI field, respectively. Currently, a Totalof N Total DAI fields need to be transmitted, with Total DAI fields 3through N defined as the fourth information field.

Applicable Embodiment 3

This applicable embodiment describes a situation where a fixed codebookis used for a part of CG and a dynamic codebook is used for another partof CG.

FIG. 7 is a schematic diagram according to Applicable embodiment 3. Asshown in FIG. 7 , there are 5 aggregated CCs, and the configurationthereof is the same as Applicable embodiment 1.

At this time, the plurality of CGs still use the counter DAI to countthe DL assignment that required to be fed back in the same slot beforethe UL grant in the mode described in Embodiment 1.

CC #4 transmits DCI including the UL grant in the last slot, whichincludes the Total DAI field at the same time. But only one Total DAIfield can be allowed to be transmitted in the current DCI. Namely, TotalDAI=3 of CG where the current UL grant will be transmitted by default.Whereas the Total DAI of CG1 cannot be transmitted, therefore, CG1cannot use a dynamic codebook but a semi-static codebook, i.e., feedbackis required for each slot of each CC in CG 1, and the CG2 may use adynamic codebook.

Determination of Codebook Size:

For CG1, the sum of the number of slots of every CC within the feedbackwindow is 2+8+4=14, the CBG configuration is 4, and the codewordconfiguration is 1, then the size of the semi-static codebook is14*4*1=56 bits.

For CG2, the size of the dynamic codebook isN_(slot)*N_(CBG)*N_(codeword)=4*8*1=32 bits;

The total number of bits is 88 bits.

It should be appreciated that, there is no CG indicated with Total DAI,since a semi-static codebook would be employed, the codebook size wouldbe related to the total number of slots, rather than the number of slotsincluding DL assignments. For this reason, the terminal can still bescheduled by the slots after the UL grant as long as within the feedbackwindow.

Applicable Embodiment 4

This applicable embodiment describes a situation where a fixed codebookis used for another part of CG and a dynamic codebook is used foranother part of CG.

FIG. 8 is a schematic diagram according to Applicable embodiment 4. Asshown in FIG. 8 , there are 5 aggregated CCs, and the configurationthereof is the same as Applicable embodiment 1.

The difference between this applicable embodiment and Applicableembodiment 3 is that the base station configuration or protocolspecifies: for CGs that do not include a UL grant, a semi-staticcodebook is fixedly used. Therefore, the CG1 determines that the dynamiccodebook will not be used from the beginning of the feedback window, andwill not include the counter DAI in the DCI including the DLassignments. This is because the function of the counter DAI is toindicate to the terminal which slots the terminal is scheduled in whichif some slots are lost therein (i.e. the terminal does not successfullydecode the PDCCH), the terminal will recognize that the counter DAI isnot continuous in the DCI that is successfully received, determine thenumber of lost slots according to the interval between the counter DAIs,and reserve the corresponding number of bits in the feedback codebook.For the semi-static codebook, no matter whether a certain slot issuccessfully received or not, and no matter whether the slot is actuallytransmitted or not, the corresponding bit number will be reserved, andsuch indication is meaningless for determining the size of thesemi-static codebook. Therefore, the DCI in which the DL assignment islocated in CG1 does not include the counter DAI.

At this time, inside the plurality of CG, the counter DAI is still usedto count the DL assignments required to be fed back in the same slotbefore the UL grant in the mode described in Applicable embodiment 1.

The CG2 may use a dynamic codebook.

Determination of Codebook Size:

For CG1, the sum of the number of slots per CC within the feedbackwindow is 2+8+4=14, CBG configuration is 4, and codeword configurationis 1, then the size of the semi-static codebook is 14*4*1=56 bits.

For CG2, the size of the dynamic codebook isN_(slot)*N_(CBG)*N_(codeword)=4*8*1=32 bits.

The total number of bits is 88 bits.

It should be appreciated that, for the CG of the semi-static codebook,the codebook size is related to the total number of slots, rather thanthe number of slots including the DL assignments, so that a terminal canstill be scheduled by the slots after the UL grant as long as within thefeedback window.

Applicable Embodiment 5

This applicable embodiment describes another situation where theaggregated CCs are grouped according to CBG configuration, a pluralityof component carrier groups (CGs) all use a dynamic codebook, and atotal downlink assignment index (Total DAI) corresponding to all CGs istransmitted in DCI of the same CC.

As mentioned in Applicable embodiment 1, if the UL grant is nottransmitted on a CC (e.g., CC #4, 30 kHz) with the largest subcarrierspacing, even if the UL grant is transmitted in the last slot of the CCwithin the feedback window, for CCs larger than 30 kHz (e.g., CC #1, 60kHz), there will be a part of the slots (last slot) that are restrictedfrom being scheduled.

To avoid this problem, as shown in FIG. 9 , it is a schematic diagramaccording to Applicable embodiment 5, the UL grant can be transmitted inthe last slot of a CC (e.g. CC #1, 60 kHz) with the largest subcarrierspacing, and at this time, all slots including the DL assignments of theplurality of CCs within a feedback window can indicate the Total DAIwithin the DCI where the UL grant is located, and there is no schedulingrestriction problem.

At this time, the system needs to support uplink scheduling between CCsspanning different TTI lengths. That is, the uplink transmission of theterminal on the second CC is scheduled on the first CC, and the first CCand the second CC have different subcarrier spacings.

Applicable Embodiment 6

This applicable embodiment describes another situation where theaggregated CCs are grouped according to subcarrier spacings, a pluralityof component carrier groups all use dynamic codebooks, and the totaldownlink assignment indexes (Total DAIs) corresponding to all CGs aretransmitted in the DCI of the same CC.

As mentioned in Applicable embodiment 1, if the UL grant is nottransmitted on a CC (e.g., CC #4, 30 kHz) with the largest subcarrierspacing, even if the UL grant is transmitted in the last slot of the CCwithin the feedback window, for CCs larger than 30 kHz (e.g., CC #1, 60kHz), there will be a part of the slots (last slot) that are restrictedfrom being scheduled.

As mentioned in Applicable embodiment 1, if a UL grant is nottransmitted on a CC (e.g., CC #4, 30 kHz) with the largest subcarrierspacing, even if the UL grant is transmitted on the last slot of the CCwithin the feedback window, for CCs larger than 30 kHz (e.g., CC #1, 60kHz), there will be a part of the slots (last slot) that are restrictedfrom being scheduled.

To avoid this problem, as shown in FIG. 10 , it is a schematic diagramaccording to Applicable embodiment 6, and for CCs larger than 30 kHz, asemi-static codebook is used in a slot after the UL grant.

In an embodiment, since the UL grant transmission time cannot judgewhether there are DL assignments in the slot in the virtual circle, whendetermining the codebook, the slots after the UL grant within thefeedback window are defined to include the DL assignments. That is,corresponding bit numbers are reserved in the feedback codebook.

For CG1, there are total 8 slots, in addition to the 7 slots includingthe DL assignments indicated by Total DAI, plus the number of slotsafter the UL grant, codebook size=8*N_(CBG)*N_(codeword)=8*4*1=32.N_(CBG)=4, and N_(codeword)=1.

For CG2, there are no slots after the UL grant within the feedbackwindow except for the 4 slots including the DL assignments indicated bythe Total DAI, so the slot number is still 4, and codebooksize=4*N_(CBG)*N_(codeword)=4*8=32, wherein N_(CBG)=8, andN_(codeword)=1.

The total feedback codebook size is 64 bits.

Applicable Embodiment 7

This applicable embodiment describes a situation where the aggregatedCCs are grouped according to subcarrier spacings, a plurality ofcomponent carrier groups all use dynamic codebooks, and the totaldownlink assignment indexes (Total DAIs) corresponding to all CGs aretransmitted in DCI of the same CC.

FIG. 11 is a diagram according to Applicable embodiment 7. As shown inFIG. 11 , a total of 5 CCs are included to operate in a CA manner, i.e.,CC #0 to CC #4. For example, configuration is shown in Table 2 which isa configuration table of CC #0 to CC #4 according to Applicableembodiment 7:

TABLE 2 CC CBG configuration Subcarrier spacing (SCS) CG #0 4 15 kHz CG1#1 4 30 kHz CG2 #2 4 30 kHz CG2 #3 8 15 kHz CG1 #4 8 60 kHz CG3

The aggregated CCs are divided into three CGs according to CBGconfiguration, CG1 including CC #0 and CC #3; CG2 including CC #1, CC#2; and CG3 including CC #4.

The counter DAI is used to count in three CGs, respectively. In otherwords, a counter DAI field is included in each DCI including the DLassignments, for indicating which number of the scheduled slots in a CGis the current slot. The counting sequence adopts a principle offrequency domain priority. That is, slots including the DL assignmentson all CCs are accumulated at the monitoring occasion of the previousPDCCH first. For example, for CG1, the terminal is scheduled by DCIs ofCC #0 and CC #3 at the first PDCCH monitoring occasion. That is, theDCIs include DL the assignments, and counter DAI fields of each DCI arerespectively indicated as 0 and 1, indicating that the current slot isthe first and second scheduled slots in the CG, respectively (note: DAIis counted from ‘0’ and is cyclically counted at a period of 4, i.e.,01230123 . . . ), such cycle count is to ensure that only 2 bits can beused to indicate any DAI value in the DCI). Next, the second PDCCHmonitoring occasion is accumulatively counted, only the DCI of CC #3schedules the terminal, and the counter DAI field of the DCI indicates2. The count of the DL assignments of all the slots before the UL grantreceived within the feedback time window is completed.

Similarly, for CG2 and CG3, the same mechanism as described above isalso used for the cumulative count of counter DAI. Similar to theApplicable embodiment 1, after the Total DAI, downlink datacorresponding to the same feedback slot is not allowed any more, i.e. asshown in the figure, the subcarrier spacing of CC #2 where the UL grantis located is 30 kHz, the UL grant is transmitted in DCI of the lastslot of 30 kHz, at this time, the last slot of CC #4 (subcarrier spacingof 60 kHz) is not allowed to schedule the terminal to feed back in thesame slot.

The Total DAI values for the three CGs are: 2, 3, and 3.

It should be appreciated that there are some CGs with different CBGconfigurations, such as CG1, CC #0 with CBG configuration 4, and CC #3with CBG configuration 8. At this time, each CC is configured accordingto the largest CBG in the CG, and feedback bits are reserved in thefeedback codebook, so that a problem can be avoided. In other words, thenumber of reserved bits cannot be determined due to the fact that theterminal cannot determine which CC the lost downlink assignment belongsto after the downlink assignment of a certain CC is lost. At this time,as long as the terminal judges that any DL assignment is lost byreceiving the counter DAI, the maximum CBG number in the reserved CG isfixed, and for CG1, and the maximum CBG number is 8. For some CCs withCBG configuration less than 8, residual bits in the feedback informationare invalid, or when the CBG configuration of the CC is a submultiple ofthe maximum CBG number, the feedback information is processedrepeatedly. For example, the number of feedback bits required for acertain slot of the CC is 4, and if feedback required be performedaccording to the maximum CBG configuration (i.e. 8) in the CG accordingto the above rule, the 4-bit feedback information is repeated twice toreach 8 bits.

For CG2, since CBG configuration of both CCs are 4, each slot includingdownlink assignment occupies 4 bits in the feedback codebook.

FIG. 12 is another schematic diagram according to Applicable embodiment7. As shown in FIG. 12 , a feedback codebook in a feedback slot for aterminal sequentially includes feedback information of the downlinkassignments in the plurality of CCs (in this applicable embodiment, itis assumed that codeword configurations of a plurality of CCs are all1), and in an embodiment, a codebook is formed in the sequence of CG1,CG2, and CG 3. Inside each CG, feedback is performed in sequenceaccording to a ‘frequency-first (frequency domain first and time domainlater)’ sequence. Taking CG1 as an example, 3 pieces of 8-bit feedbackinformation are included, wherein the first piece of 8-bit feedbackinformation corresponds to the downlink assignment in CC #0 slot 0; thesecond piece of 8-bit feedback information corresponds to the downlinkassignment in CC #3 slot 0; and the third piece of 8-bit feedbackinformation corresponds to the downlink assignment in CC #3 slot 1.

For other CG, a feedback codebook is formed by using the feedbackinformation in a similar way, and the feedback codebook is transmittedto the base station in the uplink slot indicated by the uplink grant,wherein the uplink slot indicated by the uplink grant refers to the slotfor transmitting uplink data indicated when the base station schedulesthe terminal to transmit the uplink data by using the uplink grantinformation. In an embodiment, the uplink grant may further indicate aspecific resource in a physical uplink shared channel PUSCH occupied bythe terminal for uplink data, and the feedback information is alsocarried on the PUSCH and performs puncturing transmission on the uplinkdata, or performs rate matching transmission on the uplink dataaccording to the resource occupied by the feedback information.

The present disclosure describes the generation of feedback codebooksgrouped by aggregated CCs according to subcarrier intervals and afeedback manner, because there is a direct conversion relationshipbetween the subcarrier spacing and slot length (or Transmission TimeInterval lengths, TTI lengths). That is, a subcarrier spacing of 15 kHzcorresponds to a slot length of 1 ms, a subcarrier spacing of 30 kHzcorresponds to a slot length of 0.5 ms, and a subcarrier spacing of 60kHz corresponds to a slot length of 0.25 ms, etc. Thus, the method isalso similar when the aggregated CCs are grouped according to slotlengths.

In the above embodiment, the counter DAI is used to count according tothe number of slots including downlink assignments, and the counter DAImay also be used to count according to the number of code block groups(CBGs); in one embodiment, when the counter DAI is used to count in theCG by the number of CBGs, the value of the counter DAI in the DCIincluding the DL assignments represents: accumulating CBGs in a certainsequence (such as a frequency domain first and a time domain later),until the number of CBGs included in the current slot of the current CCis reached; correspondingly, the number of downlink assignmentsindicated by Total DAI field in DCI where the UL grant is located maybe: the total number of CBGs in all slots carrying the downlinkassignment.

Applicable Embodiment 8

This applicable embodiment describes a situation where the aggregatedCCs are grouped according to codebook configuration information, theplurality of component carrier groups all use dynamic codebooks, and thetotal downlink assignment indexes (Total DAIs) corresponding to all CGsare transmitted in DCI of the same CC.

FIG. 13 is a schematic diagram according to Applicable embodiment 8. Asshown in FIG. 13 , a total of 5 CCs are included to operate in a CAmanner, i.e., CC #0 to CC #4. For the sake of simplicity of description,it is assumed in this applicable embodiment that configurations (CBGconfiguration and subcarrier spacing) of the plurality of CCs are thesame except for codewords. For example, configuration is shown in Table3 which is a configuration table of CC #0 to CC #4 according toApplicable embodiment 8:

TABLE 3 Codeword CC CBG configuration Subcarrier spacing (SCS)configuration CG #0 4 30 kHz 1 CG1 #1 4 30 kHz 1 CG1 #2 4 30 kHz 1 CG1#3 4 30 kHz 2 CG2 #4 4 30 kHz 2 CG2

The aggregated CCs are divided into two CGs according to codewordconfiguration, the codeword configuration of the CG1 is 1, namely, onecode word is transmitted in one slot and comprises CC #0, CC #1 and CC#2; the codeword configuration of CG2 is 2, i.e. two codewords aretransmits in one slot, including CC #3 and CC #4.

The counter DAI is used to count in two CGs, respectively, i.e., acounter DAI field is included in each DCI including DL assignments, forindicating which number of the scheduled slots in a CG is the currentslot. The counting sequence adopts the principle of frequency domainpriority. That is, slots including the DL assignments on all CCs areaccumulated on the previous PDCCH monitoring occasion first. Forexample, for CG1, the DL assignments are counted in the followingsequence: CC #0 slot1, CC #1 slot1, CC #2 slot1, CC #0 slot2, CC #1slot2, CC #0 slot3, CC #2 slot 3; the counter DAI sequentially has thefollowing DCI of the slot: 0, 1, 2, 3, 0, 1,2.

Similarly, CG2 counts DL assignments in the following sequence: CC #3slot0, CC #4 slot0, CC #3 slot2, CC #4 slot 2; the counter DAIsequentially has the following DCI of the slot: 0, 1, 2, 3.

Thus, the Total DAI for the two CGs are: 2 and 3. Since DAI uses cyclecounting, at this time, for CG1, Total DAI=2 indicates that there are 7slots including DL assignments.

FIG. 14 is another schematic diagram according to Applicable embodiment8. As shown in FIG. 14 , a feedback codebook at a feedback slot of aterminal sequentially includes feedback information of downlinkassignments in a plurality of CGs. Illustratively, the codebook isformed according to the sequence of CG1 and CG 2. Inside each CG,feedback is performed in sequence according to a ‘frequency-first(frequency domain first and time domain later)’ sequence. Taking CG1 asan example, since codeword configuration is 1, downlink data in one slotonly needs 4 bits of feedback information for 4 CBG configurations.Therefore, feedback for CG1 includes 7 pieces of 4-bit feedbackinformation in total, and a corresponding relationship between bits in acodebook and downlink assignment is shown in the figure.

For CG2, since codeword configuration is 2, for 4 CBG configurations,downlink data in one slot requires feedback information of 2*4=8 bits.Therefore, for CG1, the feedback includes 4 pieces of feedbackinformation of 8 bits in total, the correspondence between bits in thecodebook and downlink assignment is shown in the figure.

Note: in the above applicable embodiments, the component carriers aredivided into N CGs according to a certain factor (CBG configuration,subcarrier spacing or slot length, codeword configuration), and the CCsmay also be divided into a plurality of CGs according to a combinationof any of the above factors. For different CGs, the counter DAI is usedto count respective downlink assignment, a plurality of Total DAI fieldsare included in the DCI including the UL grant and are transmitted tothe terminal, and the terminal determines the number of downlinkassignments corresponding to the CGs by using the plurality of TotalDAIs, so that the bit number of the feedback information can bedetermined. Herein some CGs may also use a semi-static codebook, so thatthe Total DAI of the CG is not required to be transmitted and theterminal feeds back each slot in this CG.

Through the description of the foregoing embodiments, it is clear tothose skilled in the art that the method according to the foregoingembodiments may be implemented by software plus a necessary generalhardware platform, and certainly may also be implemented by hardware,but the former is a better implementation mode in many situations. Basedon such understanding, the technical solutions of the present disclosureor portions thereof that contribute to the related art may be embodiedin the form of a software product, where the computer software productis stored in a storage medium (such as a ROM/RAM, a magnetic disk, andan optical disk), and includes several instructions for enabling aterminal device (which may be a mobile phone, a computer, a server, or anetwork device) to execute the method described in the embodiments ofthe present disclosure.

Embodiment 2

In this embodiment, there is further provided a data transmissionapparatus, which is used to implement the foregoing embodiments andpreferred embodiments, and details of which will be omitted. As usedhereinafter, the term “module” may include a combination of at least oneof software and hardware that implements a predetermined function.Although the apparatus described in the embodiments below are preferablyimplemented in software, an implementation in hardware or a combinationof software and hardware is also possible and contemplated.

According to an embodiment of the present disclosure, there is furtherprovided a data transmission apparatus, including: a generation moduleand a transmission module.

The generation module is configured to generate at least one totaldownlink assignment index for a plurality of component carrier groups.

The transmission module is configured to transmit at least one totaldownlink assignment index carried in downlink control information totransmit to a receiving end.

In an embodiment, the generation module is further configured to dividethe plurality of component carriers into the plurality of componentcarrier groups according to at least one piece of: code block groupconfiguration information of component carriers; a slot length or asubcarrier spacing of the component carriers; and codeword configurationinformation of component carriers.

In an embodiment, the code block group configuration informationcomprises at least one of: the number of code block groups included in aslot; and the number of code block groups included in a transmissionblock.

In an embodiment, the code block group configuration informationincludes at least one of: the number of codewords included in a slot;and the number of codewords included in a transmission block.

In an embodiment, generating the at least one total downlink assignmentindex for the plurality of component carrier groups comprises at leastone of: each of the generated total downlink assignment indexescorresponding to a component carrier group; the number of the at leastone of the generated total downlink assignment indexes being less thanor equal to the number of the plurality of component carrier groups.

In an embodiment, the total downlink assignment index is used toindicate the number of downlink assignments required to be fed back in aspecified uplink slot before an uplink grant in the component carriergroup corresponding to the total downlink assignment index; wherein thenumber of the downlink assignments includes at least one of: the numberof slots carrying the downlink assignments; and the total number of thecode block groups in all the slots carrying the downlink assignments.

In an embodiment, the specified uplink slot comprises: an uplink slotindicated by the uplink grant.

In an embodiment, the uplink grant is transmitted in the same downlinkcontrol information with the total downlink assignment index.

In an embodiment, carrying the at least one total downlink assignmentindex in the downlink control information to transmit to the receivingend comprises at least one of: setting, in the downlink controlinformation, a first information field for carrying the at least onetotal downlink assignment index, according to the maximum number of thetotal downlink assignment indexes, wherein the bit number occupied bythe first information field is equal to the bit number required when thetotal downlink assignment indexes having the maximum number aretransmitted; setting, in the downlink control information, a secondinformation field for carrying the at least one total downlinkassignment index, according to the current number of the total downlinkassignment indexes, wherein the bit number occupied by the secondinformation field is equal to the bit number required when the totaldownlink assignment indexes having the current number are transmitted;setting, in the downlink control information, a third information fieldfor carrying one total downlink assignment index; wherein, when thenumber of the total downlink assignment indexes is more than one,information fields except the third information field in the downlinkcontrol information are multiplexed to carry residual total downlinkassignment indexes, wherein the bit number occupied by the thirdinformation field is equal to the bit number required when the one totaldownlink assignment index is transmitted; multiplexing, in the downlinkcontrol information, a specified information field in the downlinkcontrol information to carry the at least one total downlink assignmentindex; and multiplexing, in the downlink control information, thespecified information field in the downlink control information to carrythe total downlink assignment index, wherein, under the condition thatthe bit number which the specified information field is able to carry issmaller than the bit number required when a plurality of total downlinkassignment indexes are transmitted, a fourth information field to carrythe residual total downlink assignment indexes is set, wherein the bitnumber occupied by the fourth information field is equal to the bitnumber required when the residual total downlink assignment indexes aretransmitted.

In an embodiment, the specified information field in the downlinkcontrol information comprises at least one of: an indication informationfield of uplink grant timing; and an indication information field ofcode block group transmission.

In an embodiment, the third information field is used to carry a totaldownlink assignment index corresponding to a component carrier groupwhere the third information field is located.

According to another embodiment of the disclosure, there is furtherprovided a data reception apparatus, including: a reception module and adetermination module.

The reception module is configured to receive at least one totaldownlink assignment index in a downlink control information, wherein theat least one total downlink assignment index corresponds to a pluralityof component carrier groups.

The determination module is configured to determine the size of thefeedback codebook of the corresponding component carrier group accordingto the plurality of total downlink assignment indexes.

In an embodiment, the determination module is further configured to,after receiving at least one total downlink assignment index in thedownlink control information, according to the total downlink assignmentindex, the following information is determined: the number of downlinkassignments required to be fed back in a specified uplink slot before anuplink grant in the component carrier group corresponding to the totaldownlink assignment index; wherein the number of the downlinkassignments includes at least one of: the number of slots carrying thedownlink assignments; and the total number of the code block groupscarrying all the slots of the downlink assignments.

In an embodiment, the specified uplink slot comprises: an uplink slotindicated by the uplink grant.

In an embodiment, the uplink grant information and the total downlinkassignment index are received in the same downlink control information.

It should be noted that the above modules may be implemented by softwareor hardware, and for the latter, the following may be implemented, butnot limited to: the modules all located in the same processor; or, themodules located in different processors in any combination thereof.

Embodiment 3

According to another embodiment, there is further provided a processorconfigured to execute a program, wherein the program, when executed onthe processor, performs the method according to any one of the aboveoptional embodiments.

Embodiment 4

According to an embodiment of the present disclosure, there is furtherprovided a storage medium, comprising a stored program, wherein theprogram, when executed, performs the method according to any one of theabove optional embodiments.

Obviously, those skilled in the art should appreciate that theabove-mentioned modules or steps of the present disclosure may beimplemented by a general-purpose computing device, and they may beconcentrated on a single computing device or distributed in a networkcomposed of multiple computing devices, in an embodiment, they may beimplemented with program code executable by a computing device, so thatthey may be stored in a storage device and executed by the computingdevice, and in some cases, the steps shown or described may be performedin a different order than here, or they may be made separately intoindividual integrated circuit modules, or multiple modules or stepsamong them may be made into a single integrated circuit module forimplementation. In this way, the present disclosure is not limited toany specific combination of hardware and software.

1. A data transmission method, comprising: generating at least one totaldownlink assignment index for a plurality of component carrier groups;and carrying the at least one total downlink assignment index in a pieceof downlink control information to transmit to a receiving end.
 2. Themethod according to claim 1, wherein a plurality of component carriersare divided into the plurality of component carrier groups according toat least one of: code block group configuration information of thecomponent carriers; a slot length or a subcarrier spacing of thecomponent carriers; and codeword configuration information of thecomponent carriers.
 3. The method according to claim 2, wherein the codeblock group configuration information comprises at least one of: anumber of code block groups included in a slot; and a number of codeblock groups included in a transmission block.
 4. The method accordingto claim 2, wherein the codeword configuration information comprises atleast one of: a number of codewords included in a slot; and a number ofcodewords included in a transmission block.
 5. The method according toclaim 1, wherein the step of generating the at least one total downlinkassignment index for the plurality of component carrier groups comprisesat least one of: each of the generated total downlink assignment indexescorresponding to a component carrier group; the number of the at leastone of the generated total downlink assignment indexes being less thanor equal to the number of the plurality of component carrier groups. 6.The method according to claim 1, wherein the total downlink assignmentindex is configured to indicate a number of downlink assignmentsrequired to be fed back in a specified uplink slot before an uplinkgrant, in the component carrier group corresponding to the totaldownlink assignment index; wherein the number of the downlinkassignments includes at least one of: a number of slots carrying thedownlink assignments; and a total number of the code block groups in allthe slots carrying the downlink assignments.
 7. The method according toclaim 6, wherein the specified uplink slot comprises: an uplink slotindicated by the uplink grant.
 8. The method according to claim 6,wherein the uplink grant is transmitted in the same downlink controlinformation with the total downlink assignment index.
 9. The methodaccording to claim 1, wherein the step of carrying the at least onetotal downlink assignment index in the downlink control information totransmit to the receiving end comprises at least one of: setting, in thedownlink control information, a first information field for carrying theat least one total downlink assignment index, according to a maximumnumber of the total downlink assignment indexes, wherein a bit numberoccupied by the first information field is equal to a bit numberrequired when the maximum number of the total downlink assignmentindexes are transmitted; setting, in the downlink control information, asecond information field for carrying the at least one total downlinkassignment index, according to a current number of the total downlinkassignment indexes, wherein a bit number occupied by the secondinformation field is equal to a bit number required when the currentnumber of the total downlink assignment indexes are transmitted;setting, in the downlink control information, a third information fieldfor carrying one total downlink assignment index, wherein, when thenumber of the total downlink assignment indexes is more than one,information fields in the downlink control information except the thirdinformation field are multiplexed to carry residual total downlinkassignment indexes, wherein a bit number occupied by the thirdinformation field is equal to a bit number required when the one totaldownlink assignment index is transmitted; multiplexing, in the downlinkcontrol information, a specified information field in the downlinkcontrol information to carry the at least one total downlink assignmentindex; and multiplexing, in the downlink control information, thespecified information field in the downlink control information to carrythe total downlink assignment index, wherein, under the condition thatthe bit number the specified information field is able to carry issmaller than the bit number required when a plurality of total downlinkassignment indexes are transmitted, a fourth information field to carrythe residual total downlink assignment indexes is set, wherein a bitnumber occupied by the fourth information field is equal to a bit numberrequired when the residual total downlink assignment indexes aretransmitted.
 10. The method according to claim 9, wherein the specifiedinformation field in the downlink control information comprises at leastone of: an indication information field of uplink grant timing; and anindication information field of code block group transmission.
 11. Themethod according to claim 9, wherein the third information field isconfigured to carry a total downlink assignment index corresponding to acomponent carrier group where the third information field is located.12. A data reception method, comprising: receiving, in downlink controlinformation, at least one total downlink assignment index, wherein theat least one total downlink assignment index corresponds to a pluralityof component carrier groups; and determining a size of a feedbackcodebook of the corresponding component carrier group, according to theat least one total downlink assignment index.
 13. The method accordingto claim 12, wherein, after at least one total downlink assignment indexin the downlink control information is received, the total downlinkassignment index is configured to determine information of: a number ofdownlink assignments required to be fed back in a specified uplink slotbefore an uplink grant, in the component carrier group corresponding tothe total downlink assignment index, wherein the number of the downlinkassignments comprises at least one of: a number of slots carrying thedownlink assignments; and a total number of the code block groupscarrying all the slots of the downlink assignments.
 14. The methodaccording to claim 13, wherein the specified uplink slot comprises: theuplink slot indicated by the uplink grant.
 15. The method according toclaim 13, wherein the uplink grant information and the total downlinkassignment index are received in the same downlink control information.16. A data transmission apparatus, configured to perform the methodaccording to claim
 1. 17. A data reception apparatus, configured toperform the method according to claim
 12. 18. A storage medium,comprising a stored program, wherein the program, when executed,performs the method according to claim
 1. 19. A processor, configured toexecute a program, wherein the program, when executed by the processor,performs the method according to claim 1.